proof of concept of refreshing tokens from battle.net #11
+632
−331
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
this isnt really something meant to be merged in without some more code behind it.... but basically is a proof of concept of letting the users login via the browser, obtaining the token from there, and "encrypting" it, and using the browser token as your registry WEB_TOKEN. this lets user's configure their accounts via logging in with a browser as opposed to launching the game and getting it from there. also from what i've heard these tokens last a bit longer than the ones refreshed by the game, so you do not want to replace these token's w/ the ones that are in game.